So, I have created my own 

1.UX Research System, 

2.UX Test/Evaluation System, 

 

where with the help of direct user feedback, user behaviour data, experience data, usability data etc at the end of each sprint cycle We get to improve our understanding of our users i.e. mental model therefore more user centric designs can be built 

1. The current way of things;

2. The real outcome of usability testing;

3. Recommendations for improvements.

4. Criticality: Low to High

Secondary Research -> Primary Research  ​​​​​​​-> Identify the problem

List Down all the data & Reorganize as we grow our knowledge on users

All the Pain Points are then organized in High no. of people's Pain Point to lower ones with respective Goals & Metrics to gauge the Post Design Success

After observing users, I create User Personas with the details captured ( pain points & other attributes)

Top Impactful ones to Users as well as Business are considered for the First Sprint.

After Affinity Mapping, the patterns of behaviours start emerging which tell us more about our user groups who we are designing for. Not just the demographics like Age, Gender, Location, but Psychographics and their Personality Traits. This is the most important stage where in we document User Personas based on which all further design decisions are taken further in the process.

Once we create User Personas, we have a pretty much good idea about the personality traits of our users and their goals. But, what we are missing out is the situation and scenarios in which users face pain points or will be using our product. Knowing about social and environment “context” help us empathise better with our users. User scenarios can be documented in text as well as visual format through storyboarding technique.

Till this point, the team has a strong and consensus understanding about the end users needs, pain points and motivations. The Define stage of the Design Process is done. At this stage, we enter to the Design phase, We start designing the interactions between the users and the application. First step here is to make sure the users should be able to achieve their goals with minimum friction. Task Flows help us focus on just that. These are simply flow diagram, where the main focus is align these with users real life journal with offline experiences and utilise Interaction Design laws like Hicks law to reduce user cognitive load at each interaction. (Eg. Journey of going to Super Market store is what is replicated on online platforms like Flipkart, Amazon).

Imagine everything in your kitchen lying on the floor, without any categorisation and labels. Would it be easy for you to find all relevant information required. Imagine if all the chocolate cookie jars in the kitchen are put up at very easy access to kids. Is that what a mother wants for her kid, who is designing the interactions in the kitchen? Is it not important to put only primary things at easy access at first level and rest in drawers or at secondary level. Similar levels of access needs to be defined in case of mobile interaction where the users have a small real estate of screen to interact, so its very important to prioritise and provide only relevant information to users, guiding them step by step to reach their goals efficiently. Creating a sitemap at this stage helps define the information hierarchy.

At this stage, the structure gets converted into a skeleton. Similar to how a architect creates a blueprint of the entire building on paper before actually thinking of putting cement and interior design, a UX Designer create wireframes of their application on paper to quickly iterate. All design decision here are taken based on user personas, their needs and context of use.

Feedback Loop & Testing Rounds Continue

Checklist Systems i use:

UI Design System 

Additional to UX, Research , UI Systems, A Standardised System for everything is how i make sure everything is achieved & UX is maintained